Caller ID Setting

hi:
i am not sure what your GSM send to A400P, but it should be standard dtmf/fsk format. this patch is for dtmf format.

Hello Support,

I saw at Elastix website : http://www.elastix.org/content/view/15/31/lang ,en/

Elastix already support Caller ID, is this OpenVox's wctdm.c patch software available at Elastix ? If I install A400P at Elastix, shall it detect DTMF Caller ID without re-compile wctdm.c ?

Elastix Feature list
VoIP PABX:

• Caller ID supported.
• Multiple Trunk support.
• Incoming and outgoing routes with support dial pattern matching which gives flexibility
• Follow-me support
• Support for ring groups
• Support for paging and intercom for supported IP Phones
• Support for call routing based on Time Conditions
• Support for PIN sets

Thanks for your support.

Sam

i] Last edited by samsalim at 2010-4-20 19:53 [/i

hello:
=============
is this OpenVox's wctdm.c patch software available at Elastix
===============
I do not think it is a patched wctdm.c, you have to recompile that with source.

Hello,
Can you tell me what version of Elastix you need to install? Actually, Elastix and A400P natively support CallerID, but this is based on you have callerID service and you have a right country format. You know, different country the detail of CallerID is different. Meanwhile, asterisk is not include all the country format in the world. And I am not sure the details of Indonesia's Telco. But have a scan this link for more about IP PBX in your country.
http://www.voip-info.org/wiki/view/Asterisk+consultants+Asia
Anyway,please contact us as soon as possible if necessary.

Hello,

Thanks for Your help.

I use Elastix-1.6. Actually I need a ready Software to support OpenVox to provide Caller ID, maybe Elastix, PBX in Flash or anything, so I don't need to recompile wctdm.c, but if there is no way anymore, I must recompile anyway.

Thanks

sam

Hi Support,

I use A400P04 and Elastix 1.6,
1. For the the first step I copy wctdm.c patch software to zaptel-1.4.12.1/kernel
2. [root@elastix zaptel-1.4.12.1]# make
make[1]: Entering directory `/usr/local/src/zaptel-1.4.12.1'
make -C /lib/modules/2.6.18-164.el5/build ARCH=i386 SUBDIRS=/usr/local/src/zaptel-1.4.12.1/kernel HOTPLUG_FIRMWARE=yes KBUILD_OBJ_M="pciradio.o tor2.o torisa.o wcfxo.o wct1xxp.o wctdm.o wcte11xp.o wcusb.o zaptel.o ztd-eth.o ztd-loc.o ztdummy.o ztdynamic.o zttranscode.o wct4xxp/ wctc4xxp/ xpp/ wctdm24xxp/ wcte12xp/" modules
make[2]: Entering directory `/usr/src/kernels/2.6.18-164.el5-i686'

Building modules, stage 2.
MODPOST
make[2]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-i686'
make[2]: Entering directory `/usr/local/src/zaptel-1.4.12.1/kernel/xpp/utils'
cc -o print_modes -g -Wall print_modes.c
In file included from print_modes.c:3:
wctdm_fxomodes.h:93: error: redefinition of âstruct fxo_modeâ
wctdm_fxomodes.h:108: error: redefinition of âfxo_modesâ
wctdm_fxomodes.h:14: error: previous definition of âfxo_modesâ was here
make[2]: *** [print_modes] Error 1
make[2]: Leaving directory `/usr/local/src/zaptel-1.4.12.1/kernel/xpp/utils'
make[1]: *** [utils-subdirs] Error 2
make[1]: Leaving directory `/usr/local/src/zaptel-1.4.12.1'
make: *** [all] Error 2

You can see the errors, So what should I do now ? Something wrong when redefinition of fxo_modes

Sam

i] Last edited by samsalim at 2010-4-24 23:39 [/i